Skip to content

StandardModel: Formalize 6V2K5, characterize Higgs potential boundedness and minima - #2092

Merged
jstoobysmith merged 2 commits into
leanprover-community:masterfrom
kastch:feat/6V2K5
Nov 16, 2026
Merged

jstoobysmith merged 2 commits into
leanprover-community:masterfrom
kastch:feat/6V2K5

Conversation

@kastch

@kastch kastch commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

Formalizes Higgs potential TODO 6V2K5.

Potential.isBounded_iff gives the full criterion for boundedness below:
the quartic coupling is positive, or it is zero and P.μ2 <= 0.
At zero quartic coupling, only the zero field value minimizes the potential
when P.μ2 < 0; every value minimizes it when P.μ2 = 0; and there is no
minimum when P.μ2 > 0. These results concern the potential at a spacetime point.

The module documentation now follows the required format, so its lint
exemption is removed.

Validation. lake build, lake build PhyslibAlpha, and the auxiliary
script tests passed. Lean examples checked the zero-quartic cases through
import Physlib and reused the boundedness criterion in a one-doublet
limit of the 2HDM.
Linter, theorem and documentation checks passed.

AI assistance. Codex assisted with the local validation and proofs details.

Formalize 6V2K5 and use it to complete the criterion for
boundedness below. Classify the minimizing field values when the
quartic coupling vanishes.
@github-actions

github-actions Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Thank you for this pull-request (PR). If this is your first PR, welcome to the community!

While you wait for a review, note that you can review PRs too; reviewing is not restricted to maintainers. Our review guidelines explain what to look for.

Over time, contributions such as reviews, maintenance and documentation are recorded on contributions.physlib.io.

Three main points:

  • Comment -awaiting-author on its own line to remove that label from your PR.
  • Comment blocked-by-PR or -blocked-by-PR on its own line to add or remove that label, respectively.
  • The first review might take several days to arrive. If in doubt message on the Zulip.

For the author: Please read

Below is what will happen next. Please read carefully if you are not familiar with the process. You may open other PRs while this one is being reviewed, and can stack PRs on top of each other, so don't let these steps slow you down.

  1. Some automated checks will be run on your PR. You can see the results of these checks at the buttom of your PR page. If any of these checks fail, you will need to fix the issues before your PR can be merged. You can learn more about these here, including how to run them locally, which is sometimes quicker than relying on the GitHub Actions. If you have never had a PR merged before, you may have to wait for a reviewer to manually start these checks (this is for security).

  2. A reviewer will look at your PR and may ask you to make changes. This may happen a couple of days after you submit your PR, so you may need to be patient. But it should not be longer than that - if it is please bring it to the attention of the community on the Zulip. The level of review will depend on where your PR is submitted. If it is submitted to ./Physlib or ./QuantumInfo, the review will be more thorough than if it is submitted to ./PhyslibAlpha. You can find out more about what the review process is looking for in our review guidelines. If a reviewer adds an awaiting-author label to your PR, address the review comments, then please remove that label by adding a comment with -awaiting-author. This helps us keep track of reviews.

  3. The reviewer will either approve your PR, or request more changes (in which case we return to step 2). Once your PR is approved, it will be merged by a maintainer, this should happen shortly after approval, though you may get more comments at this stage.

Tip: The easiest way to get a fast review is to submit a PR that is small and self-contained, and has clear documentation explaining why things are the way they are in your changes.

If you have any problems or questions, please reach out to the community on the Zulip.

For reviewers: Summary of your PR

Found differences:
@@ Physlib.Particles.StandardModel.HiggsBoson.Potential @@
! module modified Physlib.Particles.StandardModel.HiggsBoson.Potential (+101 -31)
  namespaces StandardModel, StandardModel.HiggsField, StandardModel.HiggsField.Potential
+ added lemma isBounded_iff
+ added lemma isMinOn_iff_field_of_𝓵_zero
+ added lemma toFun_nonneg_of_𝓵_zero
! statement changed for lemma isBounded_iff_of_𝓵_zero
@@ scripts/lint/exemptions/module_doc_no_lint.txt @@
! file modified scripts/lint/exemptions/module_doc_no_lint.txt (+0 -1)
6 differences

The declarations are found by reading the diff as text, without regard for namespaces, so a declaration whose keyword and name are on different lines is missed, and two declarations of the same name in different namespaces are listed as one. A change to a proof, or to the body of a definition, does not appear. See scripts/alpha/github/pr_summary.lean.

Summary of commit f01dc6c, remade whenever a commit is pushed.

@jstoobysmith jstoobysmith left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple of small comments. Appreciate the improvements of the docs, so thanks!

@jstoobysmith

Copy link
Copy Markdown
Member

awaiting-author

@github-actions github-actions Bot added the awaiting-author A reviewer has asked the author a question or requested changes label Nov 15, 2026
@kastch

kastch commented Nov 15, 2026

Copy link
Copy Markdown
Contributor Author

-awaiting-author

@github-actions github-actions Bot removed the awaiting-author A reviewer has asked the author a question or requested changes label Nov 15, 2026

@jstoobysmith jstoobysmith left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved - will merge now.

@jstoobysmith
jstoobysmith added this pull request to the merge queue Nov 16, 2026
@jstoobysmith jstoobysmith added the ready-to-merge This PR is approved and will be merged shortly label Nov 16, 2026
Merged via the queue into leanprover-community:master with commit b313e09 Nov 16, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

medium ready-to-merge This PR is approved and will be merged shortly

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants